Determining the legitimacy of messages using a message verification process

ABSTRACT

A server computer receives an indication of an interaction between a first user device of a first user and a second user device of a second user, where the interaction includes a message for transmission from the first user to the second user. The server computer performs a verification process on the message, including performing one or more binary checks on the message. The server computer then generates a response indicating whether the message is a legitimate message based on the verification process. When the response indicates that the message is a legitimate message, the server computer transmits the message to the second user device of the second user for display.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 15/446,370,filed Mar. 1, 2017, which is hereby incorporated by reference.

FIELD

Embodiments of the invention relate to the field of networkcommunications, and more specifically, to performing a verificationprocess on interactions between computing devices.

BACKGROUND

The ability to use communications networks, including the Internet, togenerate and transmit messages between user devices, also provides acommon vulnerability: the reception of fraudulent or spammingcommunications. In situations where messages are associated with aservice provider, fraudulent messages or spam messages being received byusers of the service provider can result in a negative impact to theservice provider.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 illustrates an exemplary system according to some embodimentsdescribed herein;

FIG. 2 is a flow diagram that illustrates exemplary operations forperforming message verification, according to an embodiment; and

FIG. 3 is a block diagram illustrating a data processing system that canbe used in an embodiment.

DESCRIPTION OF EMBODIMENTS

In the following description, numerous specific details are set forth.However, it is understood, by one skilled in the art, that embodimentsof the invention may be practiced without these specific details. Inother instances, circuits, structures and techniques have not been shownin detail in order not to obscure the understanding of this description.Those of ordinary skill in the art, with the included descriptions, willbe able to implement appropriate functionality without undueexperimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

In an embodiment, a server computer performs a message verificationprocess on messages sent between computing devices or user devices. Insome embodiments, the server computer determines whether a message sentbetween two user devices is a legitimate message or is a non-legitimatemessage (e.g., spam, fraud). For example, the server computer mayreceive a message from a first user device for sending to a second userdevice. The server computer performs a verification process on themessage using a predictive model. In some embodiments, the predictivemodel uses historical data of previous messages analyzed by the servercomputer, the results of previous verification processes on the previousmessages, user-defined rules, and machine-learned rules. In someembodiments, the predictive model generates a likelihood value for themessage, the likelihood value representing a probability of the messagebeing a legitimate message.

In some embodiments, when a message has been verified as a legitimatemessage, the server computer determines whether the message was arequest message from a first user, a response message from a second userin response to a previous request message from the first user, or aresponse message from the first user in response to a response messagefrom the second user. When the message is determined to be a responsemessage from the first user in response to a response message from thesecond user, the server computer accesses a user account of the seconduser. In such embodiments, the server computer modifies the user accountof the second user. For example, the server computer modifies the useraccount of the second user by posting a charge against an account of thesecond user. In another example, the server computer modifies the useraccount of the second user by placing a notation within the user accountthat the first user responded to the response message from the seconduser.

Embodiments of the invention provide many technical advantages. Forexample, performing the message verification process on a message priorto transmitting the message to its intended destination saves bandwidthand other computing resources throughout a network by preventing thesending of data that have been identified as likely fraudulent orcontaining spam. In addition, by preventing the message from reachingits intended destination, computing resources of the destination userdevice are preserved as the destination user device does not have toprocess the fraudulent or spam message. For example, the destinationuser device does not have to dedicate resources to process or storemessages that are fraudulent or spam. In some embodiments, detectingmessages that are likely fraudulent or spam prior to the messages beingsent to its intended destination, conserves bandwidth and resources bypreventing the need to perform corrective actions when a deliveredmessage is later determined to be fraudulent or spam, such as recallingmessages or performing refunds.

Further, embodiments in which the message verification process isperformed on the message concurrently with the message being sent to theits intended destination also provide benefits. For example, byperforming the message verification at a server computer that canintercept, or otherwise receive messages on behalf of users, individualuser devices do not have to modify their systems. The server computer isable to perform and maintain the message verification operations,including updating the predictive model in a manner that does notrequire interactions by the users or from the user devices. The messagemay be delivered to the recipient, but if the message verificationprocess determines the message is fraudulent or spam, the message can bedeleted without requiring the recipient to perform any steps. This alsoallows the server computer to act as a control point where detectionthresholds can be adjusted or otherwise modified based on real-timeoperations and current vulnerabilities.

The predictive model can further allow the server computer toautomatically detect patterns of fraudulent activity. This can allow thepredictive model to determine that fraudulent activity is part of acoordinated attack. In addition, by verifying messages, the system alsocan determine whether messages are in compliance with Terms of Userestrictions.

Further, in some embodiments, the message verification process improvesthe user experience. For example, intercepting fraudulent or spammessage prevents users from being exposed to potentially fraudulentcontent, thereby improving the security and trustworthiness of thesystem from both the system and the user perspective.

FIG. 1 illustrates an exemplary network architecture that usesembodiments described herein. The system illustrated in FIG. 1 includesa first user device 102, a second user device 104, a server computer106, and a client computing device 122. In one embodiment, the servercomputer 106 is situated between user devices 102 and 104 and isconfigured to communicate with user devices 102 and 104, as well asfacilitate communications between user devices 102 and 104. Exemplaryuser devices 102 and 104 include conventional computer systems, such asa desktop computer or laptop computer, or may include devices havingcomputer functionalities such as Personal Digital Assistants (PDA),tablet computers, cellular or mobile telephones, smart-phones, or otherelectronic devices programmed to implement one or more embodiments setforth herein.

User devices 102 and 104 are configured to interact with the servercomputer 106 and can be any type of computing device capable ofreceiving user input as well as transmitting and/or receiving data via anetwork or a collection of networks—such as the Internet, a corporateIntranet, a Virtual Private Network (VPN), a Local Area Network (LAN), aWireless Local Area Network (WLAN), a cellular network, a Wide AreaNetwork (WAN), a Metropolitan Area Network (MAN), or a combination oftwo or more such networks. The network may be wired, wireless, or acombination of both. In one embodiment, the network uses standardcommunications technologies and/or protocols.

The embodiment of the server computer 106 illustrated in FIG. 1 includesmessaging module 108, message verification module 110, web server 112,and notifications module 114. This embodiment also includes model datadatabase 116, user account database 118, and messages database 120.Other embodiments may include fewer or additional modules and databasesthan those depicted in FIG. 1.

The messaging module 108 is configured to receive or detect interactions(e.g., messages) sent between user devices 102 and 104. In someembodiments, the messaging module 108 receives voice-based messagesand/or text-based messages. For example, messages can be in the form ofemail messages, text messages, voice messages, etc. In some embodiments,the messaging module 108 intercepts messages sent between user devices102 and 104. In other embodiments, messages are sent through the servercomputer 106 and received by the messaging module 108.

The message verification module 110 is configured to perform averification process on the messages received by the messaging module108 from one of user devices 102 and 104 for sending to the other ofuser device 102 and 104. In some embodiments, the message verificationmodule 110 performs the verification process on a message prior totransmitting the message to the destination. In other embodiments, themessage verification module 110 performs the verification process on amessage after, or in parallel, to transmitting the message to thedestination. In embodiments where the verification process is performedafter or in parallel to transmitting the message, the message can berecalled or deleted in response to the verification process determiningthat the message is fraudulent or spam. In some embodiments, theverification process includes performing one or more binary checks onthe message. In some embodiments, the message verification module 110analyzes the message, identifies keywords within the message, appliesthe identified keywords to a predictive model, and generates alikelihood value representing a probability of the message being alegitimate message.

In some embodiments, the result of the verification process on a messageproduces one of two results: legitimate (e.g., not spam) andnon-legitimate (e.g., spam). In some embodiments, the messages may beflagged by the system with the appropriate designation indicating theresult of the verification process, and then can be processed by themessaging module 108 based on the flag. In some embodiments, messagesthat are marked as legitimate can proceed normally to the intendeddestination of the message. In some embodiments, message that are markedas being non-legitimate may be prevented from being transmitted to theintended destination. In some embodiments, messages marked as beingnon-legitimate are stored in the messages database 120. In otherembodiments, messages marked as being non-legitimate are deleted.

In other embodiments, the result of the verification process on amessage may produce an additional result: indeterminate. In someembodiments, messages marked as indeterminate can be sent for furtheranalysis. For example, the messages marked as indeterminate can be sentto the client computing device 122 to perform a manual review.

In one embodiment, each of user devices 102 and 104 executes a networkapplication that is capable of transmitting and/or receiving networktraffic. For example, the network application may be a web browser orother application that can access network resources (e.g., web pages,images, word processing documents, PDF files, movie files, music files,or other computer files) using the network application. The web server112 links the server computer 106 to one or more user devices 102 and104 (e.g., via a network) by accepting requests (e.g., messages) fromuser devices 102 and 104 and/or transmitting web pages or otherweb-related content to user devices 102 and 104, such as image files,audio files, video files, Java applets, Flash, XML, JavaScript,Cascading Style Sheets (CSS), etc. In some embodiments, web server 112is configured to utilize a set of one or more network interfaces to sendand receive messages across a network.

In some embodiments, the web server 112 (additionally or alternately)utilizes messaging module 108 to send and/or receive interactions (e.g.,messages) to user devices 102 and 104 or between user devices 102 and104. In some embodiments, the messaging module 108 is operative to sendand/or receive instant messages, queued messages (e.g., email), text andSMS (Short Message Service) messages, voice messages, or utilize anyother suitable messaging technique.

The notifications module 114 is configured to generate notificationmessages indicating the result of the verification process performed bythe message verification module 110. The notification messages can begenerated for internal use by the message verification module 110, orcan be sent to the intended destination (e.g., the second user device104). For example, the notification message can be sent to inform thesecond user associated with the second user device 104 that the servercomputer 106 handled a message that was determined to be anon-legitimate message. The notification message can also inform thesecond user associated with the second user device 104 that correctiveactions were taken with respect to a user account of the second user inresponse to the determination that the message was a non-legitimatemessage.

The model data database 116 stores data used by the predictive model.The predictive model uses the data to determine whether the messagesreceived by the server computer 106 are legitimate message ornon-legitimate messages. In some embodiments, the model data database116 stores a list of blacklisted phrases or keywords. For example,blacklisted phrases or keywords can indicate that the message includesone or more of a payment scam, profanity, soliciting sex, have lowintent to hire, is in a non-supported language, is looking for freeservices, and/or is from a minor, among other things. The blacklistedphrases or keywords can be pre-established within the system or can belearned by the system based on a history of previous messages analyzed.

The user account database 118 stores account data for users of thesystem. In some embodiments, the account data includes user information,include contact information, payment information (e.g., payment accountinformation), professional services offered, and previous bids providedby users.

The messages database 120 stores a history of previous messages sentthrough the server computer 106, including an indication of whether eachof the messages was determined to be a legitimate message or anon-legitimate message. In some embodiments, the history of previousmessages in the messages database 120 is used by the messageverification module 110 with data stored in the model data database 116to refine the predictive model used to determine whether a message islegitimate or not legitimate.

Exemplary client computing device 122 includes conventional computersystems, such as a desktop computer or laptop computer, or may includedevices having computer functionalities such as Personal DigitalAssistants (PDA), tablet computers, cellular or mobile telephones,smart-phones, or other electronic devices programmed to implement one ormore embodiments set forth herein.

FIG. 2 is a flow diagram that illustrates exemplary operations forperforming message verification according to an embodiment. Theoperations of FIG. 2 will be described with reference to the exemplaryembodiment of FIG. 1. However, it should be understood that theoperations of FIG. 2 can be performed by embodiments of the inventionother than those discussed with reference to FIG. 1, and the embodimentsdiscussed with reference to FIG. 1 can perform operations different thanthose discussed with reference to FIG. 2.

At operation 205, the server computer 106 receives an indication of aninteraction between a first user device 102 of a first user and a seconduser device 104 of a second user. In the example described herein, theinteraction includes a message for transmission from the first userdevice 102 to the second user device 104. In other situations, theinteraction includes a message for transmission from the second userdevice 104 to the first user device 102. In some embodiments, themessage may be a response message from the second user device 104 sentin reply to an initial request message sent by the first user device 102to the server computer 106 and retrieved by the second user device. Forexample, message may be a request message from the first user device 102requesting a service to be performed, and the message may be a responsemessage from the second user device 104 that includes a proposal relatedto the service request. In some embodiments, the message may be anadditional response message sent from the first user device 102 to thesecond user device 104 in response to the response message from thesecond user device 104. For example, the message may be a responsemessage sent from the first user device 102 to the second user device104 responding to the response message from the second user device 104that included the proposal related to the service request.

In some embodiments, the server computer 106 receives the indication ofthe interaction between the first user device 102 and the second userdevice 104 when the server computer 106 receives the message from thefirst user device 102. In some embodiments, the message is received overa network from the first user device 102. In some embodiments, theserver computer 106 stores the received interaction (e.g., message) in amessages database 120.

In some embodiments, the server computer 106 receives the indication ofthe interaction between the first user device and the second user device104 when the interaction is performed using an interface provided by theserver computer 106. For example, the server computer 106 may beassociated with a website or an application that facilitates theinteractions. In other embodiments, the server computer 106 receives theindication of the interaction when the interaction is performed using acommunication means linked to the server computer 106. For example, theserver computer 106 may provide a unique contact method (e.g., phonenumber, email address, meeting scheduling software), where the uniquecontact method can be tracked by the server computer 106 to identifywhen an interaction has occurred.

Next, the flow proceeds to operation 210, where a message verificationmodule 110 performs a verification process on the message included aspart of the interaction between the first user device 102 and the seconduser device 104. In some embodiments, as part of the verificationprocess, the message verification module 110 accesses the model datadatabase 116. In some embodiments, the model data database 116 includesblacklisted keywords and/or phrases and the type of non-legitimatemessages the blacklisted keywords and/or phrases correspond to. In someembodiments, the model data database 116 includes user-inputted ormachine-learned rules or content that are indicative of fraud, or areotherwise non-legitimate, as well as rules or content that areindicative of legitimate communications. Examples of content indicativeof a non-legitimate message include, but are not limited to thefollowing:

Types of Non- Legitimate Messages Example Banned User Message sent fromblacklisted email address, phone number, or other contact means Messagesent from a banned user Profanity Message contains profanity orinappropriate language Payment Scam Message contains poor grammarImmediately discusses payment. Very little discussion of the jobdetails. Message asks if user will accept credit cards or cashier checksMessage mentions health problems (e.g., recovering from cancer, heartproblem, hearing impaired) Message indicates urgency (e.g., “urgent”,“ASAP”, “right now”) User tries to take message off of the providedplatform. Message contains contact information not associated with theuser account (e.g., different email address or phone number)Inappropriate User is trying to hire user for competing businessSolicitation Mention their own business and benefits working for themMessage includes requests for inappropriate services from the userMessages from User is a minor (under 18 years of age) Minors Messageincludes content indicating the user is a minor (e.g., “high school”,“prom”, describes kid activities) Messages in Message contains contentin languages that are Unsupported not supported by the system LanguagesBartering/ Users looking for users who will do the work for Seeking Freefree for a charity/non-profit (e.g., “donate”, Services “free”,“charity”) Garbled Message does not make sense Messages Low/No IntentMessages contain words indicating the user is not to Hire interested inproposal received from another user (e.g., “not interested”, “no, thankyou”)

In some embodiments, the message verification module 110 may alsoperform one or more binary checks on the message. In such embodiments,the message verification module 110 compares the identified keywords toinformation stored in the model data database 116. In such embodiments,the message verification module 110 can determine if one or more of theidentified keywords is a blacklisted keyword. For example, the messageverification module 110 can mark messages from banned users, bannedemails, or banned phone numbers, as being non-legitimate. In anotherexample, the message verification module 110 can mark messagescontaining profanity, inappropriate solicitation, and/or indicating lowor no intent to hire, as non-legitimate. In another example, the messageverification module 110 determines if the message is associated with avalid name or user name. In some embodiments, determining if the name oruser name is valid is based on a history of previous messages processedby the server computer 106 and/or using third party data (e.g., censusdata).

In some scenarios, the result of the verification process performed bythe message verification module 110 may be indeterminate. In suchsituations, the message may be sent to a manual review process. In someembodiments, the messaging module 108 transmits the message to a clientcomputing device 122, and the result of the manual review can be sentback to the server computer 106 by the client computing device 122. Inother embodiments, the server computer 106, by default, marks themessage as non-legitimate when the message verification module 110cannot determine its legitimacy. In other embodiments, the default ruleis to mark the message as a legitimate message and process the messagesimilarly to messages determined to be legitimate messages.

In some embodiments, the message verification module 110 generates aresult of the verification process automatically and distributes theresult. In other embodiments, after the message verification module 110generates the rule, the result is further processed through a clientcomputing device 122 for a manual review.

In the embodiment depicted in FIG. 2, the message verification module110 is executed by the server computer 106. In other embodiments, themessage verification module 110 is executed by another computer separatefrom the server computer (e.g., client computing device 122).

At operation 215, based on the result of the message verificationprocess, server computer 106 generates a response indicating whether themessage is a legitimate message. For example, when the generatedlikelihood value is at or above an established threshold, the messagecan be determined to be legitimate. In contrast, when the generatedlikelihood value is below an established threshold, the message can bedetermined to be non-legitimate. In some embodiments, the servercomputer 106 flags the message as being legitimate or non-legitimate. Insome embodiments, the response indicating whether the message is alegitimate message or a non-legitimate message is generated by thenotifications module 114.

At operation 220, when the message is determined to be a legitimatemessage, the flow proceeds to operation 225. When the message isdetermined to be a non-legitimate message, the flow proceeds tooperation 245.

At operation 225, in response to the server computer 106 determiningthat the message is a legitimate message, the messaging module 108transmits the message to its destination (e.g., the second user device104). In some embodiments, the messaging module 108 transmits themessage to the second user device 104 using an appropriate communicationmeans, such as over a communications network. In some embodiments, themessage is transmitted to the second user device 104 without anyalteration to the message as initially sent by the first user device102. In other embodiments, the message is transmitted to the second userdevice 104 with an indication that the message was verified by theserver computer 106 as a legitimate message prior to the message beingsent to the second user device 104.

In some embodiments, the messaging module 108 transmits the message tothe second user device 104 by displaying the message on a user interfaceassociated with the server computer 106. For example, the message may betransmitted for display on a website or application associated with theserver computer 106. In other embodiments, the messaging module 108transmits the message display within a messaging application (e.g., anemail or text message application) stored on the second user device 104.

At operation 230, the server computer 106 determines if the message wassent in response to a previous message. In some embodiments, the servercomputer 106 may distinguish between various types of messages,including, but not limited to: (1) a request message made by a firstuser, (2) a message sent from a second user to the first user inresponse to the request message, and (3) a response message from thefirst user in response to the message sent from the second user to thefirst user. In some embodiments, different types of messages triggerdifferent operations to be performed by server computer 106.

When the message is a response message from the first user in responseto the message sent from the second user to the first user (e.g., type3), the flow proceeds to operation 235. For example, the message may bea response message from the first user responding to a previous messagesent from the second user to the first user, where the previous messagefrom the second user included the proposal related to the initialrequest made by the first user. When the message is a request message(e.g., type 1) or a message sent in response to a request message (e.g.,type 2), the flow proceeds to operation 245.

At operation 235, the server computer 106 modifies a user account of thesecond user associated with the second user device 104. In someembodiments, the server computer 106 accesses the user account database118 to retrieve the user account data associated with the user accountof the second user. In some embodiments, the server computer 106modifies the user account of the second user. For example, because thefirst user responded to the second user's response message, and themessage was verified as a legitimate message by the message verificationmodule 110, the server computer 106 may post a charge to the useraccount of the second user.

At operation 240, in response to the server computer 106 determiningthat the message is a non-legitimate message, the messaging module 108prevents the message from being transmitted to its intended destination(e.g., the second user device 104). In some embodiments, where themessage was sent from a user device associated with a user account, theserver computer 106 accesses the user account database 118 to flag theuser account that sent the message to indicate that a non-legitimatemessage was sent from the user account. In some embodiments, thenotifications module 114 generates a notification to send to the seconduser device 104 indicating that the first user attempted to send anon-legitimate message to the second user device 104 of the second user.

At operation 245, the server computer 106 stores the message in amessages database 120. In some embodiments, the message is stored in themessages database 120 when the message is determined to be legitimateand/or when the message is determined to be non-legitimate. In someembodiments, the messages stored in the messages database 120 can beused by the message verification module 110 to refine the predictivemodel used to determine whether subsequent messages received by theserver computer 106 are legitimate or non-legitimate.

In the embodiment described with respect to FIG. 2, the messageverification process is applied to the message prior to the messagebeing sent to its destination (e.g., the second user device 104). In analternative embodiment, the message is sent by the server computer 106to the second user device 104 prior to, or concurrently with, themessage verification module 110 performing the verification process onthe message. In such an embodiment, assuming the message from the firstuser device 102 was determined to be a response to a response messagefrom the second user device 104, the user account associated with thesecond user is potentially modified by the server computer 106, asdescribed with respect to operation 235 in FIG. 2, prior to determiningwhether the message was a legitimate message or a non-legitimatemessage. In such a situation, in the event the message verificationmodule 110 determines that the message was a non-legitimate message, theserver computer 106 performs corrective measures on the user account ofthe second user. For example, the server computer 106 may modify theuser account of the second user to credit back a charge that was appliedto the user account of the second user. The notifications module 114 mayalso generate a notification message indicating that a previous messagewas determined to be a non-legitimate message and a credit has beenposted to the user account of the second user. The notification messagecan then be transmitted to the second user device 104 by the messagingmodule 108. In addition, in response to the message being determined tobe non-legitimate, the server computer 106 can automatically delete, orotherwise remove, the message from the account of the second user.

In the event the message verification module 110 determines that themessage was a legitimate message, the server computer 106 does not needto take additional action, as the user account of the second user hasalready been modified.

As illustrated in FIG. 3, the computer system 300, which is a form of adata processing system, includes the bus(es) 350 which is coupled withthe processing system 320, power supply 325, memory 330, and thenonvolatile memory 340 (e.g., a hard drive, flash memory, Phase-ChangeMemory (PCM), etc.). The bus(es) 350 may be connected to each otherthrough various bridges, controllers, and/or adapters as is well knownin the art. The processing system 320 may retrieve instruction(s) fromthe memory 330 and/or the nonvolatile memory 340, and execute theinstructions to perform operations described herein. The bus 350interconnects the above components together and also interconnects thosecomponents to the display controller & display device 370, input/outputdevices 380 (e.g., NIC (Network Interface Card), a cursor control (e.g.,mouse, touchscreen, touchpad, etc.), a keyboard, etc.), and the optionalwireless transceiver(s) 390 (e.g., Bluetooth, Wi-Fi, Infrared, etc.). Inone embodiment, the client device, caching system, and/or service devicedescribed herein may take the form of the computer system 300.

The techniques shown in the figures can be implemented using code anddata stored and executed on one or more computing devices (e.g., clientdevices, servers, etc.). Such computing devices store and communicate(internally and/or with other computing devices over a network) code anddata using machine-readable media, such as machine-readable storagemedia (e.g., magnetic disks; optical disks; random access memory; readonly memory; flash memory devices; phase-change memory) andmachine-readable communication media (e.g., electrical, optical,acoustical or other form of propagated signals—such as carrier waves,infrared signals, digital signals, etc.). In addition, such computingdevices typically include a set of one or more processors coupled to oneor more other components, such as one or more storage devices, userinput/output devices (e.g., a keyboard, a touchscreen, and/or adisplay), and network connections. The coupling of the set of processorsand other components is typically through one or more busses and bridges(also termed as bus controllers). The storage device and signalscarrying the network traffic respectively represent one or moremachine-readable storage media and machine-readable communication media.Thus, the storage device of a given computing device typically storescode and/or data for execution on the set of one or more processors ofthat computing device. Of course, one or more parts of an embodiment ofthe invention may be implemented using different combinations ofsoftware, firmware, and/or hardware.

While the flow diagrams in the figures show a particular order ofoperations performed by certain embodiments of the invention, it shouldbe understood that such order is exemplary (e.g., alternativeembodiments may perform the operations in a different order, combinecertain operations, overlap certain operations, etc.).

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

1-20. (canceled)
 21. A computer-implemented method comprising: receivinga first indication of a first interaction between a first user device ofa first user and a second user device of a second user, the firstinteraction including a first message for transmission from the firstuser to the second user; performing, by a message verification system, averification process on the first message, the verification process onthe first message including: identifying keywords in voice content ortext content of the first message, performing a binary check on thefirst message, including: comparing the keywords to information storedin a database, and determining whether one or more of the keywords is ablacklisted keyword, when there is not a blacklisted keyword in thefirst message, applying the keywords to a predictive model, andgenerating a likelihood value representing a probability of the firstmessage being legitimate based on the application of the keywords to thepredictive model; generating a first response indicating that the firstmessage is a legitimate message based on the verification process;responsive to the first response indicating that the first message islegitimate, performing the following: transmitting the first message tothe second user device of the second user for display on the second userdevice, and determining that the first message is a response message toa previous message sent from the second user device to the first userdevice, and responsive to this determination, modifying a user accountassociated with the second user including posting a charge to the useraccount
 22. The computer-implemented method of claim 21, furthercomprising: receiving a second indication of a second interactionbetween a third user device of a third user and a fourth user device ofa fourth user, the second interaction including a second message fortransmission from the third user device to the fourth user device;performing, by the message verification, the verification process on thesecond message; generating a second response indicating that the secondmessage is not a legitimate message based on the verification process;responsive to the second response indicating that the second message isnon-legitimate, preventing the transmission of the second message to thefourth user device.
 23. The computer-implemented method of claim 21,wherein the predictive model is based on a history of previouslegitimate messages and non-legitimate messages determined by themessage verification system.
 24. The computer-implemented method ofclaim 21, further comprising: receiving a second indication of a secondinteraction between the first user device and the second user device,the second interaction including a second message for transmission fromthe first user device to the second user device; transmitting the secondmessage to the second user device; modifying the user account associatedwith the second user; performing the verification process on the secondmessage; and in response to determining that the second message is anon-legitimate message, performing corrective measures on the useraccount associated with the second user, the corrective measuresincluding an additional modification to the user account associated withthe second user.
 25. The computer-implemented method of claim 24,wherein the corrective measures include performing a refund process onthe user account associated with the second user.
 26. Thecomputer-implemented method of claim 24, wherein the corrective measuresinclude removing the second message from the user account associatedwith the second user.
 27. A non-transitory machine-readable storagemedium that provides instructions that, when executed by a processor,cause said processor to perform operations comprising: receiving a firstindication of a first interaction between a first user device of a firstuser and a second user device of a second user, the first interactionincluding a first message for transmission from the first user to thesecond user; performing, by a message verification system, averification process on the first message, the verification process onthe first message including: identifying keywords in voice content ortext content of the first message, performing a binary check on thefirst message, including: comparing the keywords to information storedin a database, and determining whether one or more of the keywords is ablacklisted keyword, when there is not a blacklisted keyword in thefirst message, applying the keywords to a predictive model, andgenerating a likelihood value representing a probability of the firstmessage being legitimate based on the application of the keywords to thepredictive model; generating a first response indicating that the firstmessage is a legitimate message based on the verification process;responsive to the first response indicating that the first message islegitimate, performing the following: transmitting the first message tothe second user device of the second user for display on the second userdevice, and determining that the first message is a response message toa previous message sent from the second user device to the first userdevice, and responsive to this determination, modifying a user accountassociated with the second user including posting a charge to the useraccount.
 28. The non-transitory machine-readable storage medium of claim27, further comprising: receiving a second indication of a secondinteraction between a third user device of a third user and a fourthuser device of a fourth user, the second interaction including a secondmessage for transmission from the third user device to the fourth userdevice; performing, by the message verification, the verificationprocess on the second message; generating a second response indicatingthat the second message is not a legitimate message based on theverification process; responsive to the second response indicating thatthe second message is non-legitimate, preventing the transmission of thesecond message to the fourth user device.
 29. The non-transitorymachine-readable storage medium of claim 27, wherein the predictivemodel is based on a history of previous legitimate messages andnon-legitimate messages determined by the message verification system.30. The non-transitory machine-readable storage medium of claim 27,further comprising: receiving a second indication of a secondinteraction between the first user device and the second user device,the second interaction including a second message for transmission fromthe first user device to the second user device; transmitting the secondmessage to the second user device; modifying the user account associatedwith the second user; performing the verification process on the secondmessage; and in response to determining that the second message is anon-legitimate message, performing corrective measures on the useraccount associated with the second user, the corrective measuresincluding an additional modification to the user account associated withthe second user.
 31. The non-transitory machine-readable storage mediumof claim 30, wherein the corrective measures include performing a refundprocess on the user account associated with the second user.
 32. Thenon-transitory machine-readable storage medium of claim 30, wherein thecorrective measures include removing the second message from the useraccount associated with the second user.
 33. An apparatus, comprising: aprocessor; and a non-transitory machine-readable storage medium coupledwith the processor that stores instructions that, when executed by theprocessor, cause said processor to perform the following: receive afirst indication of a first interaction between a first user device of afirst user and a second user device of a second user, the firstinteraction including a first message for transmission from the firstuser to the second user; perform, by a message verification system, averification process on the first message, the verification process onthe first message including: identifying keywords in voice content ortext content of the first message, performing a binary check on thefirst message, including: comparing the keywords to information storedin a database, and determining whether one or more of the keywords is ablacklisted keyword, when there is not a blacklisted keyword in thefirst message, applying the keywords to a predictive model, andgenerating a likelihood value representing a probability of the firstmessage being legitimate based on the application of the keywords to thepredictive model; generate a first response indicating that the firstmessage is a legitimate message based on the verification process;responsive to the first response indicating that the first message islegitimate, performing the following: transmitting the first message tothe second user device of the second user for display on the second userdevice, and determining that the first message is a response message toa previous message sent from the second user device to the first userdevice, and responsive to this determination, modifying a user accountassociated with the second user including posting a charge to the useraccount.
 34. The apparatus of claim 33, wherein the instructions furthercause said processor to perform the following: receive a secondindication of a second interaction between a third user device of athird user and a fourth user device of a fourth user, the secondinteraction including a second message for transmission from the thirduser device to the fourth user device; perform, by the messageverification, the verification process on the second message; generate asecond response indicating that the second message is not a legitimatemessage based on the verification process; responsive to the secondresponse indicating that the second message is non-legitimate, preventthe transmission of the second message to the fourth user device. 35.The apparatus of claim 33, wherein the predictive model is based on ahistory of previous legitimate messages and non-legitimate messagesdetermined by the message verification system.
 36. The apparatus ofclaim 33, wherein the instructions further cause said processor toperform the following: receive a second indication of a secondinteraction between the first user device and the second user device,the second interaction including a second message for transmission fromthe first user device to the second user device; transmit the secondmessage to the second user device; modify the user account associatedwith the second user; perform the verification process on the secondmessage; and in response to determining that the second message is anon-legitimate message, perform corrective measures on the user accountassociated with the second user, the corrective measures including anadditional modification to the user account associated with the seconduser.
 37. The apparatus of claim 36, wherein the corrective measuresinclude performing a refund process on the user account associated withthe second user.
 38. The apparatus of claim 36, wherein the correctivemeasures include removing the second message from the user accountassociated with the second user.